5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
- Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-7: Predefined Fields

DISPOSITION


This is the input process that a designer uses to allow the end user to choose a printer, or choose whether to print a report or log to the screen, or whether to submit a process to background.If DISPOSITION is not invoked, any subsequent output will be directed to the screen or printer according to the defaults set in system administration.

This process, shown below, can be invoked at any time, but must not be invoked as DETACHED, and must not be specified as a 'Separate Task' (in other words, a designer should never allow this process to be submitted to background).If either of these parameters are wrong, the invocation will have no effect.

Before invoking this process, the designer can override the default values by modifying the corresponding PRINT? or SUBMIT? predefined fields.If the PDFs are modified using SET statements in the Pre-Invocation event point, the user will still be able to manually modify the value.However, if the PDFs are modified by using child constraints, the values will display but cannot be changed by the user.

Disposition Predefined Process

Load Settings.  Retrieve a previously saved Disposition.

Save Settings.  Allow the operator the ability to save the Disposition settings on this screen for later retrieval.

User Defined.  Allow for you to pass parameters directly to the print spooler as part of the print file configuration file (.cfg).

Submit to Background.  If the end user selects the submit to background option, DISPOSITION invokes the DISPOSITION (BACKGROUND) predefined input process as a subprocess.

Application Design Manual                                         "Powered by Appx Software"

1147

©2006 By APPX Software, Inc. All Rights Reserved